home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: app_defs
- Date: Thu, 28 Jul 94 09:17:34 BST
- From: C.J.Ridd@computer-science.birmingham.ac.uk
- Precedence: bulk
-
- Warwick writes:
- >It may be useful to have a `type' code for each atrribute-value pair in
- >the app_defs.sys file, to facilitate editing via a tool. For example:
- >
- >
- >*.papyrus*.key.openFile: KEY = ^O
- >*.papyrus*.font: FNT = Gemini 10pt
- >*.papyrus*.key.newFile: KEY = 0x00380402=F1 // Pretend this is the F1 code
- >*.papyrus*.fgColor*: COL = Purple
- >*.papyrus*.bgColor*: COL = 0x00150315 // Pretend this is a nice colour
- >*.tempFile*: FIL = f:\tmp
- >*.foo.name*: TXT = Hello World
- >
- ><attribute-pattern> ":" <type> "=" <value>
-
- The type would not be required if we could more completely specify the
- attribute-pattern string. eg <application name>.<function>.<attribute>
- papyrus.opendoc.key "^O"
- papyrus.opendoc.name "Open..."
- papyrus.default.font "ITC Garamond Book 11pt"
- papyrus.default.geometry 800x600+0+0
- *.tmpdir.name U:\tmp
-
- Each standard 'function' (not sure this is the best word for it) would
- have a number of well-defined attributes like in the example above.
-
- Different types for the values could be handled, perhaps you want to
- define a key in terms of a scancode.
- aardvark.find.key 0x01020304
-
- I'm uncertain about the idea of application-types... How many dtp
- packages or word processors is a user likely to have? Would it really
- be *useful* to be able to define a different key for 'Quit' just for
- image processing apps?
-
- >chrisridd:
- >>What we *should* be doing, IMHO, is proposing and voting for the
- >>existence of a shortcut file or files, and only then discussing the
- >>precise contents of it. The whole voting period should be much shorter
- >>too, as this list is very active :-) Say two weeks per vote.
- >
- >Voting before discussion? That's not very democratic. It's like voting
- >for a parliament, THEN letting them discuss policy.
-
- Well, you missed my point (or maybe I didn't make it too well :-)
- which was that we should all *agree* to the principle of having a
- such-and-such, and only then fully defining it. Maybe voting on the
- principle would be too strong though...
-
- >Preclude discussion and you end up with
- >the type of standards comittees you often get in industry: where
- >everyone is just trying to make THEIR PRODUCT the standard, regardless
- >of its merits.
-
- Hmmm. This sounds mighty similar to the gem toolkit discussion/flame fest.
-
- --Chris
-
- X.400: g=chris;s=ridd;o=nhs imc;ou1=cosit;a=attmail;p=nhs imc;c=gb
- Cix: chrisridd@cix
-
-